Connection and disconnection of shared audio endpoint

ABSTRACT

Systems and methods are disclosed for connection and disconnection of a shared audio endpoint. In one aspect, a method includes detecting a charging event of a user mobile device being electrically coupled to a charger, and in response to detecting the charging event, broadcasting a beacon comprising a name of a shared audio endpoint. The shared audio endpoint accepts a connection request to connect the user mobile device to the shared audio endpoint based on the beacon.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit under 35 U.S.C. § 120 to U.S. patentapplication Ser. No. 16/383,395 filed on Apr. 12, 2019. U.S. patentapplication Ser. No. 16/383,395 claims benefit under 35 U.S.C. § 119 toU.S. Provisional Patent Application Ser. No. 62/657,627, filed on Apr.13, 2018, entitled, “Call Audio Endpoint for Hoteling” and having thesame inventor. U.S. patent application Ser. No. 16/383,395 and U.S.Provisional Patent Application Ser. No. 62/657,627 are incorporatedherein by reference in their entirety.

BACKGROUND

Bluetooth wireless technology is a communication technology for devicesto exchange data over short distance using radio waves. Bluetooth®wireless technology is owned by the Bluetooth Special Interest Group,located in Kirkland Wash. Since development, Bluetooth® wirelesstechnology has been used for many different functions. One commonfunction is the transference of audio signal between devices. Forexample, Bluetooth® wireless technology may be used for call andrecorded audio streaming between a user mobile device and a shared audioendpoint. The shared audio endpoint has a speaker and, optionally, amicrophone, to play and possibly record audio.

In order to use a shared audio endpoint, the user mobile device and theshared audio endpoint perform a pairing operation whereby both the usermobile device and the shared audio endpoint discover each other,exchange permissions for communicating, and store identifyinginformation about each other in local memory. The shared audio endpointand the user mobile device may be concurrently paired and disconnectedfrom multiple devices. For communication, the shared audio endpoint andthe user mobile device are first connected, and then may have audiosignal transmitted between the devices. A shared audio endpoint may beshared amongst multiple user mobile devices, whereby the shared audioendpoint is paired with the multiple user mobile device. Even thoughshared, the shared audio endpoint is often limited to only beingconnected to a single user mobile device at a time.

In some cases, the user mobile device automatically connects to theshared audio endpoint when in Bluetooth® wireless technology range ofthe shared audio endpoint. Moreover, for the single user mobile deviceto stop being connected to the shared audio endpoint while still inBluetooth® wireless technology range for communication, the usermanually disconnects the user mobile device from the shared audioendpoint.

SUMMARY

In general, systems and methods are disclosed for connection anddisconnection of a shared audio endpoint. In one aspect, a methodincludes detecting a charging event of a user mobile device beingelectrically coupled to a charger, and in response to detecting thecharging event, broadcasting a beacon comprising a name of a sharedaudio endpoint. The shared audio endpoint accepts a connection requestto connect the user mobile device to the shared audio endpoint based onthe beacon.

In one aspect, a system comprises a charger, a wireless technologyinterface, and processing circuitry connected to the charger and thewireless technology interface. The processing circuitry is configured todetect a charging event of a user mobile device being electricallycoupled to the charger. Also, the processing circuitry is configured to,in response to detecting the charging event, broadcast a beaconcomprising a name of the shared audio endpoint. Further, the processingcircuitry is configured to accept a connection request to connect theuser mobile device to a shared audio endpoint based on the beacon.

In one aspect, a system comprises a charger, a wireless technologyinterface, and processing circuitry connected to the charger and thewireless technology interface. The processing circuitry is configured todetect a charging event of a user mobile device being electricallycoupled to the charger. Also, the processing circuitry is configured to,in response to detecting the charging event, connect the user mobiledevice to the system via the wireless technology interface.

Other aspects of the invention will be apparent from the followingdescription and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a diagram of a system in accordance with one or moreembodiments.

FIGS. 2, 3, 4, 5, 6, and 7 shows flowcharts in accordance with one ormore embodiments.

FIG. 8 shows an example in accordance with one or more embodiments.

DETAILED DESCRIPTION

Specific embodiments of the invention will now be described in detailwith reference to the accompanying figures. Like elements in the variousfigures are denoted by like reference numerals for consistency.

In the following detailed description of embodiments of the invention,numerous specific details are set forth in order to provide a morethorough understanding of the invention. However, it will be apparent toone of ordinary skill in the art that the invention may be practicedwithout these specific details. In other instances, well-known featureshave not been described in detail to avoid unnecessarily complicatingthe description.

Throughout the application, ordinal numbers (e.g., first, second, third,etc.)

may be used as an adjective for an element (i.e., any noun in theapplication). The use of ordinal numbers is not to imply or create anyparticular ordering of the elements nor to limit any element to beingonly a single element unless expressly disclosed, such as by the use ofthe terms “before”, “after”, “single”, and other such terminology.Rather, the use of ordinal numbers is to distinguish between theelements. By way of an example, a first element is distinct from asecond element, and the first element may encompass more than oneelement and succeed (or precede) the second element in an ordering ofelements.

In general, embodiments of the invention are directed to connectionsbetween a shared audio endpoint and a user mobile device. Specifically,one or more embodiments at least in part uses a signal strength of aBluetooth Low Energy (BLE) signal to set the connection status. The BLEsignal has less range than a standard Bluetooth® wireless technologyconnection. Thus, even though audio signal may be transmitted using thestandard Bluetooth® wireless technology connection without quality loss,a connected user mobile device may be disconnected from the shared audioendpoint. As used throughout the application, the term audio signal andaudio recording are any signal or recording, respectively, that at leastincludes and audio component and may also include other multimediacomponents, such as visual and tactile components.

By way of an example, consider the following scenario. Multiple userseach have at least one corresponding mobile phone that the users use forwork. The users may share a conference room that has a conference calldevice having a Bluetooth® wireless technology enabled speaker andmicrophone system for conference calls. When a set of users enter aconference room, the conference call device should connect to the userwith the greatest signal strength. Thus, the user, from the collectionof users that enters the conference room, who wants to user their mobilephone for a conference call only needs to place their mobile phone nextto the conference call device. After the meeting and if the conferencecall is over, when the user leaves the conference room with their mobilephone to go to their office next door to the conference room, theconference call device should disconnect the Bluetooth® wirelesstechnology connection from the user's mobile device. Thus, any call thatthe user receives is not connected via the user's mobile device back tothe conference room that the user left. Rather, the call should beconnected to the speaker in the user's office.

Turning now to the Figures, FIG. 1 shows a diagram of a system inaccordance with one or more embodiments. As shown in FIG. 1, the systemincludes a shared audio endpoint (100) and a user mobile device (102). Ashared audio endpoint (100) is a physical device that is an endpoint foran audio signal. In other words, the shared audio endpoint (100) is adevice that is at least configured to convert between electrical audiosignal and sound waves. As such, the shared audio endpoint (100)includes one or more microphones and/or one or more speakers. The one ormore microphones and/speakers may be integrated within the housing ofthe shared audio endpoint and/or external to the housing, such as bybeing wired or wirelessly connected to the shared audio endpoint. Forexample, the shared audio endpoint may include an integrated speaker andmicrophone as well as a headset, whereby the headset has the speaker andmicrophone. In the example, the headset may be wired or wirelesslyconnected to the shared audio endpoint. In one or more embodiments, theshared audio endpoint (100) is configured to be concurrently sharedamongst multiple user mobile devices (e.g., user mobile device (102))(described below). In other words, the shared audio endpoint is able tobe concurrently paired with multiple user mobile devices.

Continuing with the shared audio endpoint, the shared audio endpoint(100) at least includes a Bluetooth® wireless technology connectioninterface (104), processing circuitry (106), and, optionally, a chargingconnection (108). In one or more embodiments, the Bluetooth® wirelesstechnology connection interface (104) is hardware that is configured toconvert between electrical signal to radio signal in accordance with theBluetooth® wireless technology standard. The processing circuitry (106)corresponds to hardware circuitry, such as one or more applicationspecific integrated circuit (ASIC) and/or central processing unit (CPU)of the shared audio endpoint (100) that is configured to processinstructions.

The charging connection (108) is an interface for charging the usermobile device (102). For example, the charging connection (108) may be awireless charger, such as a charging pad containing an induction coilthat can be aligned with a coil of the mobile device to charge themobile device. By way of another example, the charging connection (108)may be a wired connector, such as a universal serial bus (USB)interface. In one or more embodiments, signal through the chargingconnection is only an electrical signal for charging the user mobiledevice (102) and not a data signal.

Although not shown, the shared audio endpoint (100) may includeadditional components. Such other components may include temporaryand/or persistent storage, keypad, touchpad, touchscreen, display, andother user or phone interface.

A user mobile device (102) is a mobile device of a user that is in apath of the audio signal. For example, in the case of playback, the usermobile device (102) may have storage that stores an audio recording. Inthe case of a call, the user mobile device (102) is a device thatconnects to a cell network or other wireless network to connect the userto the call. For example, the user mobile device may be a mobile phone,a mobile computing system (e.g., a laptop computer, tablet, or othercomputing device), a gaming device, or other mobile device.

The user mobile device (102) includes a Bluetooth® wireless technologyconnection interface (110), processing circuitry (114), and a connectionprogram (112). The user mobile device (102) may include additionalcomponents, such as a cellular modem, Wi-Fi interface, touch sensitivedisplay, and/or one or more electromechanical buttons. Although notshown, the shared audio endpoint (100) may include additionalcomponents. Such other components may include temporary and/orpersistent storage, keypad, touchpad, display, and other user or phoneinterface.

The Bluetooth wireless technology connection interface (110) is hardwareon the user mobile device (102) that is configured to convert betweenelectrical signal to radio signal in accordance with the Bluetooth®wireless technology standard. The processing circuitry (114) on the usermobile device is hardware circuitry configured to process instructions,such as to provide or receive the audio signal via the Bluetooth®wireless technology connection interface (110).

The processing circuitry may be configured to execute a connectionprogram (112). The connection program (112) is software and/or firmwarethat is configured to implement the user mobile device side of theBluetooth® wireless technology connection to the shared audio endpoint(100). For example, the connection program (112) may be a native programor an installed program that is configured to perform the functionalityof FIGS. 2, 5, and/or 7.

The shared audio endpoint (100) and/or the user mobile device (102) areconfigured to transmit and/or receive a Bluetooth® wireless technologyaudio signal (116). The Bluetooth® wireless technology audio signal(116) is an audio signal transmitted via radio waves in accordance withthe Bluetooth® wireless technology standard. In one or more embodiments,the Bluetooth® wireless technology audio signal (116) is transmittedusing Bluetooth® wireless technology. Bluetooth® wireless technology isa point to point communication. The Bluetooth® wireless technologyoperates in the 2400-2483.5 mega Hertz (MHz) range within theindustrial, scientific, and medical (ISM) 2.4 giga Hertz (GHz) radiofrequency band. The Bluetooth® wireless technology may be basic rateand/or enhanced data rate Bluetooth® wireless technology. In theBluetooth® wireless technology, the audio signal is split into packetsand exchanged, as the Bluetooth® wireless technology audio signal (116),through one of seventy nine designated Bluetooth® wireless technologychannels, whereby each channel has 1 MHz bandwidth. Additional data maybe similarly transmitted via the Bluetooth® wireless technology.

The shared audio endpoint (100) and/or the user mobile device (102) arefurther configured to transmit and/or receive a BLE beacon (120). A BLEbeacon is a radio signal transmitted intermittently that includesidentifying information about the transmitter of the beacon, whereby thetransmitter is either the shared audio endpoint (100) or user mobiledevice (102). In one or more embodiments, the BLE beacon is transmittedat regular intervals. For example, the interval may be ten times everysecond. BLE uses at most one megabit per second and consumes around 0.1to 0.5 watts of energy. The identifying information may be a name,number, or address (e.g., media access control (MAC)) assigned to thetransmitter.

Although FIG. 1 shows a single shared audio endpoint and a single usermobile device, multiple shared audio devices and user mobile devices mayexist. For example, a single user may have multiple user mobile devices,multiple users may have multiple user mobile devices. Further, multipleshared audio endpoints may exist, where the multiple shared audioendpoints are within Bluetooth® wireless technology range of each other.

Turning now to the flowcharts, FIGS. 2, 3, 4, 5, 6, and 7 showsflowcharts in accordance with one or more embodiments. While the varioussteps in these flowcharts are presented and described sequentially, oneof ordinary skill will appreciate that some or all of the steps may beexecuted in different orders, may be combined, or omitted, and some orall of the steps may be executed in parallel. Furthermore, the steps maybe performed actively or passively. For example, some steps may beperformed using polling or be interrupt driven in accordance with one ormore embodiments of the invention. By way of an example, determinationsteps may not require a processor to process an instruction unless aninterrupt is received to signify that condition exists in accordancewith one or more embodiments of the invention. As another example,determination steps may be performed by performing a test, such aschecking a data value to test whether the value is consistent with thetested condition in accordance with one or more embodiments of theinvention.

By way of an overview, FIG. 2 shows a flowchart from a user mobiledevice perspective with a shared audio endpoint broadcasting a BLEbeacon. FIG. 3 shows a flowchart from the shared audio endpointperspective with the shared audio endpoint broadcasting the beacon. FIG.4 shows a flowchart from a user mobile device perspective with the usermobile device broadcasting a BLE beacon. FIG. 5 shows a flowchart fromthe shared audio endpoint perspective with the user mobile devicebroadcasting the beacon. FIG. 6 shows a flowchart with chargingtriggering the connection of the user mobile device to the shared audioendpoint. FIG. 7 shows a flowchart for disconnecting, by the sharedaudio endpoint, the user mobile device from the shared audio endpoint.

Turning to FIG. 2, in Step 201, the connection program on the usermobile device listens for a broadcast beacon. The connection program maybe a background process executing on the user mobile device thatregularly checks for a BLE beacon. As another example, the Bluetooth®wireless technology interface may trigger an interrupt to the connectionprogram when a BLE beacon is received. In some embodiments, theconnection program is specific to the shared audio endpoint. In suchembodiments, the connection program may be preinstalled by a user, orinstallation may be triggered with the pairing process. For example, aspart of an initial Bluetooth wireless technology communication with theshared audio endpoint, the shared audio endpoint may triggerinstallation of the connection program on the user mobile device.

In Step 203, a determination is made whether a BLE beacon is receivedfrom the shared audio endpoint. As shown by the No arrow on Step 203 inFIG. 2, the connection program, periodically or based on an interrupt,determines whether a BLE beacon is received. Regardless, the user mobiledevice may continue processing other tasks.

If a BLE beacon is received, in Step 205, a determination is madewhether the user mobile device has been paired with the shared audioendpoint. The BLE beacon is a broadcasted signal that includes theidentifying information (described above) about the shared audioendpoint. The identifying information may be in a token of the beacon.Thus, the user mobile device may compare the identifying informationwith stored identifiers of paired devices to determine whether the usermobile device has been previously paired with the shared audio endpoint.Any previous pairing may be based on a received BLE beacon or triggeredmanually.

If the user mobile device is not previously paired with the shared audioendpoint, the user mobile device pairs with the shared audio endpoint inStep 207. The pairing process is performed in accordance with theBluetooth® wireless technology protocol. The pairing is performed toestablish a connection between the two devices to authorize the devicesto communicate and store identifying information about each device inthe respective set of known devices. To pair manually, the shared audioendpoint and/or the user mobile devices are set in a discoverable mode(“discoverable device”). If pairing based on the BLE beacon, the sharedaudio endpoint is in discoverable mode. The other device will requestconnecting with the discoverable device. The discoverable deviceprovides a type of device and a name assigned to the device. Afterrequesting connection, the devices exchange authentication information,such as one or more passkeys, which is then validated. If valid, thenthe devices are paired. The user mobile device and the shared audioendpoint store the identifying information about the user mobile deviceor the shared audio endpoint.

After pairing or if a determination is made that the devices are alreadypaired, the user mobile device connects to the shared audio endpoint inStep 209. Specifically, the connection program sends a connectionrequest to the shared audio endpoint. The connection allows forBluetooth® wireless technology audio signals in accordance withBluetooth® wireless technology to be transmitted between the sharedaudio endpoint and the user mobile device. In some embodiments, the usermobile device may be connected to only a single audio endpoint fortransmitting audio signal at a time. In some embodiments, the sharedaudio endpoint may be connected to only a single user mobile device at atime. Thus, if the shared audio endpoint is an endpoint for phone calls,the shared audio endpoint only manages a single phone call at a time. InStep 211, the user mobile device disconnects from the shared audioendpoint. The disconnection may be performed manually or in accordancewith the discussion below with reference to FIG. 7.

FIG. 3 shows a flowchart for the shared audio endpoint to connected to auser mobile device based on the shared audio endpoint issuing abroadcast beacon in accordance with one or more embodiments. In one ormore embodiments, the shared audio endpoint only broadcasts a BLE beaconwhen the shared audio endpoint is not currently connected any usermobile device. In Step 301, the shared audio endpoint broadcasts beaconinformation including identifying information. The broadcast is a widebroadcast of a BLE beacon. Namely, a short radio signal is transmittedby the shared audio endpoint in accordance with BLE technology. In Step303, the shared audio endpoint accepts a connection request from theuser mobile device as the audio endpoint for the user mobile device.Accepting the connection request establishes a Bluetooth® wirelesstechnology connection between the shared audio endpoint and the usermobile device. Thus, the shared audio endpoint and the user mobiledevice may communicate using Bluetooth® wireless technology.Disconnection may be performed manually or in accordance with FIG. 7.

FIGS. 4 and 5 show flowcharts for establishing a connection when theuser mobile device broadcasts a BLE beacon. FIG. 4 shows a flowchartfrom the user mobile device perspective. In Step 401, the user mobiledevice pairs with the shared audio endpoint. Pairing with the sharedaudio endpoint may be manually triggered, triggered by a connectionrequest from the shared audio endpoint (e.g., such as received afterStep 409), or triggered by a connection program of the shared audioendpoint. In Step 403, the user mobile device connects with the sharedaudio endpoint. In Step 405, the user mobile device disconnects from theshared audio endpoint. The connection and disconnection from the sharedaudio endpoint may be performed as discussed above with reference toSteps 209 and 211 of FIG. 2.

In Step 407, the user mobile device broadcasts a beacon with identifyinginformation. The beacon broadcasted by the user mobile device is a BLEbeacon that uses only a short burst of radio signal that is distributedwidely rather than point to point. For example, the connection programmay trigger the intermittent broadcast of the BLE beacon.

In Step 409, a determination is made whether a connection request isreceived from the shared audio endpoint. For example, the connectionprogram on the user mobile device may determine whether a shared audioendpoint transmitted a connection request. The connection request may betransmitted, for example, via Bluetooth® wireless technology. As shownby the No arrow from Step 409, the user mobile device may intermittentlybroadcast the beacon until a connection request is received or until anexit condition exists (not shown).

If a connection request is received, the user mobile device accepts theconnection request from the shared audio endpoint in Step 411.Specifically, a Bluetooth® wireless technology connection is establishedbetween the user mobile device and the shared audio endpoint. In Step413, the user mobile device uses the shared audio endpoint for audioinput and/or output. In the case of a telephone call, the user mobiledevice uses the shared audio endpoint as a user interface for the call.Disconnection may be performed manually or in accordance with FIG. 7.

FIG. 5 shows a flowchart for the user mobile device to transmit thebeacon from the shared audio endpoint perspective. In Step 501, theshared audio endpoint pairs with the user mobile device. The pairingwith the shared audio endpoint may be manually triggered on shared audioendpoint, triggered by the beacon (e.g., such as received in Step 509),or triggered by the user mobile device. In Step 503, the shared audioendpoint connects with the user mobile device via a Bluetooth® wirelesstechnology connection. In Step 505, the shared audio endpointdisconnects from the user mobile device. The connection anddisconnection from the user mobile device may be performed as discussedabove with reference to FIGS. 2 and 3.

In Step 507, the shared audio device listens for a beacon. In someembodiments, the shared audio device listens for a beacon only when theshared audio device is not connected to another user mobile device. Insome embodiments, the shared audio device continually listens for abeacon regardless of whether only the shared audio device is connectedto another user mobile device. For example, the Bluetooth® wirelesstechnology connection interface may monitor radio waves to detect a BLEbeacon. In some embodiments, the monitoring of a beacon is only withpreviously paired devices or known devices. Because the beacon includesidentifying information, the shared audio endpoint is able to comparethe identifying information with a set of stored identifiers todetermine whether the beacon is received from a known device. In otherembodiments, any BLE beacon received may trigger a possible connectionafter pairing is performed. A determination is made whether a beacon isreceived in Step 509. If a beacon is not received, the flow may continuewith Step 507.

In Step 511, a determination is made whether the received signalstrength indicator (RSSI) value satisfies a connection threshold.Specifically, a determination is made whether the RSSI value indicatesat least a threshold level of signal strength that is predefined in theconnection threshold. The RSSI value of the beacon is determined by theshared audio endpoint. The shared audio endpoint compares the RSSI valueto the connection threshold. If the RSSI value is not greater than theconnection threshold, the flow may return to Step 507 to continue tolisten for a beacon. If the RSSI value satisfies the connectionthreshold, then the flow proceeds to Step 513.

In one or more embodiments, the connection threshold for the BLE beaconmay be configurable. Further the connection threshold may be set higherthan the level of data packet loss through Bluetooth® wirelesstechnology connection. Specifically, the connection threshold may be setsuch that a user mobile device should be within the same room as theshared audio endpoint or within a few feet of the shared audio endpoint.For example, the connection threshold may be 90 in the range of 0-100,wherein 100 is the highest signal strength.

By enforcing a high connection threshold, the shared audio endpointmakes sure that user mobile device to which the shared audio endpoint isconnecting is within the same vicinity as the shared audio endpoint.Thus, the shared audio endpoint may be used in an office sharingenvironment or a conferencing environment in which several shared audioendpoint devices and user mobile device may be within Bluetooth®wireless technology range of each other.

Moreover, if the RSSI value is set so high as to allow only a few feetto connect, the shared audio endpoint may be used in a conference roomwith multiple user mobile devices concurrently paired with the sharedaudio endpoint. In such a scenario, the user that wants to use theiruser mobile device for conferencing purposes only has to place theiruser mobile device within the few feet of the shared audio endpointregardless of the order that the user mobile device enter Bluetooth®wireless technology range of the shared audio endpoint.

Continuing with FIG. 5, if the shared audio endpoint receives a beaconsatisfying the connection threshold, the flow proceeds to Step 513. InStep 513, the shared audio endpoint connects to the user mobile device.Specifically, the shared audio endpoint sends a connection request tothe user mobile device via Bluetooth® wireless technology signal.Although not shown in FIG. 5, In some embodiments, if multiple BLEbeacons from different user mobile devices are received within athreshold interval of time, the shared audio endpoint may send theconnection request to the user mobile device having the strongest RSSIsignal that satisfies the connection threshold. Based on the connectionrequest, the connection is established as described above in referenceto FIG. 4. Disconnection may be performed manually or in accordance withFIG. 7.

FIG. 6 shows a flowchart for connecting based on a charging event. InStep 601, the shared audio endpoint detects a charging event of the usermobile device being connected to the charger. In particular, a sensor ofthe shared audio endpoint may detect the initiation of charging the usermobile device for charging, such as when the user mobile device isplaced on the charging pad.

In Step 603, a determination is made whether to select a user mobiledevice for connection based on the signal strength. The shared audioendpoint may be preconfigured to select based on an ordered list orbased on the signal strength. If based on the ordered list, the flowproceeds to Step 605, where the shared audio endpoint traverses theordered list of paired user mobile devices to identify a first usermobile device in the ordered list that is within Bluetooth® wirelesstechnology connection range of the shared audio endpoint. In someembodiments, the Bluetooth® wireless technology connection range alsoincludes the RSSI value being greater than the connection threshold. Insome embodiments, the Bluetooth® wireless technology connection range issuch that a threshold number of packets are not dropped.

Returning to Step 603, if a determination is made to select based on thesignal strength value, the flow proceeds to Step 607. In Step 607, theuser mobile device having the strongest signal strength is selected. Forexample, based on the RSSI value, the signal strength of the user mobiledevices is determined and used to select a user mobile device. In such ascenario, the user mobile device that is connected to the charger of theshared audio endpoint may be selected based on being the most adjacentto the shared audio endpoint.

In one or more embodiments, the shared audio endpoint may be configuredto be in a personal mode. The configuration may be a user selectableoption of the shared audio endpoint. In other words, the user selectableoption may be to either be in shared mode or be in personal mode. Inshared mode, a charging event may cause the shared audio endpoint toperform one or more of the Steps described above in reference to FIG. 6.However, in the personal mode, the shared audio endpoint may be pairedor otherwise identify a single particular user mobile device to whichthe shared audio endpoint is to connect. Thus, the shared audio endpointmay automatically connect to the single user mobile device upon acharging event. Specifically, the charging event in the personal modetriggers the connection to the single particular user mobile device thatis set in the personal mode. For example, upon detecting that a usermobile device has started to wirelessly charge from the shared audioendpoint, the shared audio endpoint may initiate the formation of aBluetooth wireless link with the previously-paired user mobile device.

Once connection is established between the shared audio endpoint and theuser mobile device, the connection may be monitored for a disconnectionevent. For example, the disconnection may be manual or based on an RSSIvalue. FIG. 7 shows a flowchart for determining when to disconnect bythe shared audio endpoint. A similar set of steps may be performed bythe user mobile device in accordance with one or more embodiments.

In Step 701, the connection to the user mobile device is monitored. Inparticular, the RSSI value of the Bluetooth® wireless technologyconnection is monitored. In Step 703, a determination is made whetherthe signal strength of the connection satisfies a disconnectionthreshold. In one or more embodiments, the RSSI value of the connectionis monitored and determined whether the RSSI value satisfies adisconnection threshold. The RSSI value satisfies the disconnectionthreshold when the signal strength is less than the signal strength setforth in the disconnection threshold. Further, the disconnectionthreshold is set such that the signal strength is well above the signalstrength that packets drop due to a weak signal starts to occur. Forexample, the disconnection threshold may be 50% of the signal strengthabove which packet drop occurs. By way of an example, the RSSI value maybe set as 75 or lower. If the RSSI value does not satisfy thedisconnection threshold, then the connection monitoring continues inStep 701.

If the connection satisfies the disconnection threshold, the flowproceeds to

Step 705. In Step 705, a determination is made whether an activecommunication stream exists. Active communication occurs when packets ofaudio signal are continuing to be exchanged between the user mobiledevice and the shared audio endpoint using the Bluetooth® wirelesstechnology. In other words, a determination is made whether a Bluetooth®wireless technology audio signal is being transmitted. If an activecommunication stream is determined to exist, the flow returns to Step701 to continue to monitor the connection.

If the active communication stream does not exist, the flow proceeds toStep 707 to close the connection with the user mobile device. As such,the connection between the user mobile device and the shared audiodevice ends. As shown in FIG. 7, the connection ends when both theconnection satisfies the disconnection threshold and an activecommunication stream does not exist. In other words, the failing tosatisfy the disconnection threshold by itself does not trigger thedisconnection of the user mobile device.

Although not shown, packet drop occurring due to a weak signal may alsocause disconnection even when the active communication connectionexists. Such an event may occur, for example, if the user mobile deviceis in an active communication with the shared audio endpoint and movingaway from the shared audio endpoint. At a threshold distance that ismuch farther than the distance corresponding to the disconnectionthreshold, the shared audio endpoint is no longer within range that aBluetooth® wireless technology connection may be maintained. In such ascenario, the connection is closed with the user mobile device.

The following example is for explanatory purposes only and not intendedto limit the scope of the invention. As described above, one or moreembodiments may be used in an office sharing environment in which sharedcall audio endpoints are shared between users. FIG. 8 shows an exampleof such an office environment (800) in accordance with one or moreembodiments. In the example, a conference room (804) is adjacent to fourwork cubicles (806, 808, 810, 812). As shown by key (802), each of theconference room (804) and four work cubicles (806, 808, 810, 812)include a shared call audio endpoint. The shared call audio endpoint inthe example is a device that has desk phone features while allowingusers to use their mobile phones for calls. Thus, the user may keep thesame phone number at their desk using their desk phone, continueconversations when leaving their desk using their desk phone, etc.Further, without configuration besides pairing, the users may continueto use the phone number of their mobile phone and have the keypad,speaker phone, handset, and interface of a desk phone. The shared callaudio device may further include a headset with a built in microphone.

Because of the adjacency of the conference room (804) and four workcubicles (806, 808, 810, 812) along with the open office design, thevarious shared call audio devices are within Bluetooth® wirelesstechnology range of each other. In other words, packet drop does notoccur due to the signal strength. Thus, under standard methods, when auser moves from one of the cubicles to the other or from the conferenceroom back to a desk, the user's mobile phone is still connected to theprior connected shared audio device.

By way of an example of one or more embodiments, consider the scenarioin which Ted gets to work first and wants to work at cubicle (810). Fredgets to work next and selects cubicle (812). Ann and Fran select cubicle(808) and cubicle (806), respectively. Each user, when they arrive,place their mobile phones on the charging pad of the cubicles respectiveshared call audio endpoint. Because of the charging event, a Bluetooth®wireless technology connection is established between the respectiveshared call audio endpoint and the user's mobile phone. For example, thecharging event may cause the shared call audio endpoint to select theuser's mobile phone according to the RSSI value. Thus, the users makecalls by using the handset and headset of the respective shared callaudio endpoint, and the call is routed through the user's mobile phone.

Continuing with the example, Fred and Ann have a meeting in theconference room 804. When Ann leaves her cubicle (808), the RSSI valueis less than the disconnection threshold, so Ann's mobile phonedisconnects from her shared call audio endpoint. The shared call audioendpoint of the conference room (804) issues a BLE beacon, whichtriggers Ann's mobile phone to connect. She and Fred have a conferencecall with others not at the office using Ann's mobile phone. Even if,while having her mobile phone (e.g., in her pocket), she briefly returnsto cubicle (808) during the conference call to get her computer from herdesk, the conference call does not disconnect from the shared call audioendpoint of the conference room (804) because an active communicationstream is determined to exist.

At the end of the conference call, Ann and Fred leave the conferenceroom (804). Because a call does not exist (i.e., no active communicationstream), the shared call audio endpoint of the conference room (804)disconnects. Thus, Ann's mobile phone is free to connect back to theshared call audio endpoint in cubicle (808). The shared call audioendpoint in the conference room (804) is then available to connect toanother mobile device, such as Fran or Ed's mobile phone in a subsequentconference call.

Software instructions in the form of computer readable program code toperform embodiments of the invention may be stored, in whole or in part,temporarily or permanently, on a non-transitory computer readable mediumsuch as a CD, DVD, storage device, a diskette, a tape, flash memory,physical memory, or any other computer readable storage medium.Specifically, the software instructions may correspond to computerreadable program code that, when executed by a processor(s), isconfigured to perform one or more embodiments of the invention.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

What is claimed is:
 1. A method comprising: detecting a charging eventof a user mobile device being electrically coupled to a charger, inresponse to detecting the charging event, broadcasting a beaconcomprising a name of a shared audio endpoint, and accepting, by theshared audio endpoint, a connection request to connect the user mobiledevice to the shared audio endpoint based on the beacon.
 2. The methodof claim 1, further comprising: monitoring a connection between the usermobile device and the shared audio endpoint; making, while monitoring, afirst determination that a signal strength of the connection between theuser mobile device and the shared audio endpoint is less than adisconnection threshold; making, while monitoring, a seconddetermination that an active communication stream does not exist betweenthe user mobile device and the shared audio endpoint; and closing theconnection between the shared audio endpoint and the user mobile devicein response to both the first determination and the seconddetermination.
 3. The method of claim 2, further comprising: making,while monitoring, a third determination that the signal strength of theconnection between the user mobile device and the shared audio endpointis less than the disconnection threshold; making, while monitoring, afourth determination that the active communication stream exists betweenthe user mobile device and the shared audio endpoint; and continuingmonitoring the connection between the user mobile device and the sharedaudio endpoint based on the fourth determination despite the thirddetermination.
 4. The method of claim 1, wherein detecting the chargingevent comprises detecting the user mobile device on a wireless chargingpad located on the shared audio endpoint.
 5. The method of claim 1,wherein detecting the charging event comprises detecting an inductivecoupling between the charger and the user mobile device.
 6. The methodof claim 1, wherein detecting the charging event comprises detecting theuser mobile device being connected via charging only universal serialbus (USB) connection to the charger.
 7. The method of claim 1, furthercomprising: detecting that a received signal strength from the usermobile device is greater than a connection threshold, wherein connectingthe user mobile device is further in response to the received signalstrength being greater than the connection threshold.
 8. A systemcomprising: a charger; a wireless technology interface; and processingcircuitry, connected to the charger and the wireless technologyinterface, for: detecting a charging event of a user mobile device beingelectrically coupled to the charger, in response to detecting thecharging event, broadcasting a beacon comprising a name of a sharedaudio endpoint, and accepting a connection request to connect the usermobile device to the shared audio endpoint based on the beacon.
 9. Thesystem of claim 8, wherein the processing circuitry is further for:monitoring a connection between the user mobile device and the sharedaudio endpoint; making, while monitoring, a first determination that asignal strength of the connection between the user mobile device and theshared audio endpoint is less than a disconnection threshold; making,while monitoring, a second determination that an active communicationstream does not exist between the user mobile device and the sharedaudio endpoint; and closing the connection between the shared audioendpoint and the user mobile device in response to both the firstdetermination and the second determination.
 10. The system of claim 9,wherein the processing circuitry is further for: making, whilemonitoring, a third determination that the signal strength of theconnection between the user mobile device and the shared audio endpointis less than the disconnection threshold; making, while monitoring, afourth determination that the active communication stream exists betweenthe user mobile device and the shared audio endpoint; and continuingmonitoring the connection between the user mobile device and the sharedaudio endpoint based on the fourth determination despite the thirddetermination.
 11. The system of claim 9, wherein the charger is awireless charging pad located on the shared audio endpoint, and whereindetecting the charging event comprises detecting the user mobile deviceon the wireless charging pad.
 12. The system of claim 9, whereindetecting the charging event comprises detecting an inductive couplingbetween the charger and the user mobile device.
 13. The system of claim9, further comprising: universal serial bus (USB) port to the charger,wherein detecting the charging event comprises detecting a connectionwith the USB port.
 14. The system of claim 9, wherein the processingcircuitry is further for: detecting that a received signal strength fromthe user mobile device is greater than a connection threshold, whereinconnecting the user mobile device is further in response to the receivedsignal strength being greater than the connection threshold.
 15. Asystem comprising: a charger; a wireless technology interface; andprocessing circuitry, connected to the charger and the wirelesstechnology interface, for: detecting a charging event of a user mobiledevice being electrically coupled to the charger; and in response todetecting the charging event, connecting the user mobile device to thesystem via the wireless technology interface.
 16. The system of claim15, wherein the charger is a wireless charging pad.
 17. The system ofclaim 16, wherein the charger creates an inductive coupling with theuser mobile device.
 18. The system of claim 15, wherein the chargingevent is the user mobile device being connected via charging onlyuniversal serial bus (USB) connection to the charger.
 19. The system ofclaim 15, wherein the processing circuitry is further for: detectingthat a received signal strength from the user mobile device is greaterthan a connection threshold, wherein connecting the user mobile deviceis further in response to detecting the charging event and to thereceived signal strength being greater than the connection threshold.20. The system of claim 19, wherein the user mobile device is selectedfrom a plurality of user mobile devices based on the received signalstrength from each of the plurality of user mobile devices.